Techniques for Moving Data between a Network Input/Output Device and a Storage Device

ABSTRACT

Examples are disclosed for moving data between a network input/output (I/O) device and a storage subsystem and/or storage device. In some examples, a network I/O device coupled to a host device may receive a data frame including a request to access a storage subsystem or storage device. The storage subsystem and/or storage device may be located with the network I/O device or separately coupled to the host device through a storage controller. One or more buffers maintained in a cache for processor circuitry may be used to exchange control information or stage data associated with the data frame to avoid or eliminate use of system memory to move data to or from the storage subsystem and/or storage device. Other examples are described and claimed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, claims the benefit of andpriority to previously filed U.S. patent application Ser. No. 13/948,715filed Jul. 23, 2013, entitled “Techniques for Moving Data between aNetwork Input/Output Device and a Storage Device”, which is herebyincorporated by reference in its entirety.

TECHNICAL FIELD

Examples described herein are generally related to storing or readingdata from a storage subsystem based on a request included in a receiveddata frame.

BACKGROUND

Networking and storage are becoming more and more intertwined ascomputing devices are deployed in highly distributed modes of operation.For example, stored data may be distributed across many computingdevices or network nodes for a given network. The given network may beconfigured as a type of cloud-based service such as software as aservice (SAAS) or infrastructure as a service (IAAS). Typically, storageand network subsystems for individual network nodes are architecturallydesigned as separate subsystems. As a result of being on separatesubsystems, data arriving from the network to storage at a given networknode or vice versa needs to be routed between the subsystems. Often,data may be routed through system memory to move the data between thetwo subsystems.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a first example system.

FIG. 2 illustrates a second example system.

FIG. 3 illustrates an example process.

FIG. 4 illustrates an example block diagram for an apparatus.

FIG. 5 illustrates an example of a first logic flow.

FIG. 6 illustrates an example of a second logic flow.

FIG. 7 illustrates an example of a storage medium.

FIG. 8 illustrates an example of a network input/output device.

DETAILED DESCRIPTION

As contemplated in the present disclosure, data received at or to betransmitted from a network node having separate network and storagesubsystem may route the data through system memory. This type of routingwas originally used when network data capacities (e.g., bandwidth) weresuch that relatively small amounts of system memory was needed to movethe data between the subsystems. System memory was also needed due tosomewhat high access latencies for certain types of storage to includehard disk drives. However, as network data capacities have greatlyincreased, larger amounts of system memory are needed to maintain anacceptable throughput performance. Overhead and latencies associatedwith using system memory to route the data between the subsystems mayfurther degrade performance. Additionally, advances in non-volatilememory have enabled use in storage subsystems. Non-volatile memory maybe included in such storage devices as solid state drives (SSDs) thathave significantly lower access latencies. Therefore, greater networkdata capacities combined with lower access latencies for newer types ofstorage may result in use of system memory for moving data betweennetwork and storage subsystems as a less desirable and less efficientoption for moving data. It is with respect to these and other challengesthat the examples described herein are needed.

In some examples, techniques for moving data between a network (NW)input/out (I/O) device and a storage subsystem having one or morestorage devices may be implemented. For these examples, circuitry for aNW I/O device coupled to a host device may be capable of executingvarious modules to facilitate movement of the data. The various modulesmay include a receive module to receive a data frame that includes arequest to access a storage subsystem maintained at the network I/Odevice. The storage subsystem may include a storage device such as asolid state drive (SSD). The various modules may also include a buffermodule to use one or more buffers maintained in a cache for processorcircuitry included in a processor socket at the host device. The one ormore buffers may be arranged to exchange control information for therequest. The control information may be exchanged with a protocol stackexecuted by the processor circuitry. The various modules may alsoinclude a determination module to determine whether to read from orstore to the storage subsystem data associated with the request based onthe exchanged control information.

In some other examples, the techniques may also include tagging one ormore buffers maintained in a cache for processor circuitry included in aprocessor socket at a host device. For these other examples, the one ormore buffers may be tagged by a NW I/O device coupled to the host deviceto indicate use of the one or more buffers for staging data received ortransmitted via one or more network connections coupled to the NW I/Odevice. The data may be associated with requests to access a storagedevice controlled by a storage controller coupled to the host device.Also, for these other examples, a data frame may be received thatincludes a request by a remote device to access the storage device. Dataassociated with the request may then be forwarded to or received fromthe one or more tagged buffers based on whether the request is to readthe data from the storage device or the request is to store the data tothe storage device.

FIG. 1 illustrates a first example system. As shown in FIG. 1 the firstexample system includes a system 100 having a host device 105 coupled toa NW I/O device 130 and a storage controller 140 via communication links135 and 145, respectively. Also, as shown in FIG. 1, host device 105 maybe able to couple to network 150 through NW I/O device 130 viacommunication channel 140. In some examples, remote device(s) 170 mayestablish one or more network connections through communication channel160 coupled to network 150 and through communication channel 140 coupledto NW I/O device 130. For these examples, the one or more networkconnections between remote device(s) 170 and NW I/O device 130 may beused to receive data frames including requests to access a storagedevice (e.g., from among storage device(s) 142) controlled by storagecontroller 140 coupled to host device 105.

According to some examples, the terms “host computer,” “host device,”“host,” “network node,” and “node” may be used interchangeably, and maymean, for example, without limitation, one or more end stations, mobileinternet devices, smart phones, media devices, input/output (I/O)devices, tablet computers, appliances, intermediate stations, networkinterfaces, clients, and/or portions thereof. Also, in some examples,the terms “remote device” or “remote network node” may be usedinterchangeably, and may mean, for examples, without limitation, acomputing device remotely accessible (e.g., via a network connection) toa host device.

According to some examples, a “network” such as network 150 may compriseany mechanism, instrumentality, modality, and/or portion thereof thatpermits, facilitates, and/or allows two or more entities to becommunicatively coupled together. Also in some examples, a first entitymay be “communicatively coupled” to a second entity if the first entityis capable of transmitting to and/or receiving from the second entityone or more commands and/or data (e.g., included in a data frame).

In some examples, as shown in FIG. 1, host device 105 includes aprocessor socket 110. Also, as shown in FIG. 1, processor socket 110includes processor circuitry 112 and a last level cache 114. Processorcircuitry 112 may include one or more processing elements 112-1 to 112-n(where “n” represents any whole integer >1) and a buffer manager 116.Processing elements 112-1 to 112-n may represent multiple processingcores or engines included in processing circuitry 112 and buffer manager116 may part of a device driver in an instantiation executed byprocessing elements 112-1 to 112-n for an operating system for hostdevice 105. Processing elements 112-1 to 112-n may be capable of usinglast level cache 114 including buffers 115-1 to 115-m (where “m”represents any whole integer >2) to at least temporarily stage or storedata. According to some examples, buffers 115-1 to 115-m of last levelcache 114 may either be individually assigned to a given processingelement of processor circuitry 112 or may be shared among the processorelements and may include types of memory such as volatile memory havinglow access latencies and relatively small data capacities (e.g., staticrandom-access memory (SRAM)). In either case, buffer manager 116 mayrepresent logic and/or features executed by processing elements 112-1 to112-n capable of managing access to buffers 115-1 to 115-m and tofacilitate possible movement of data between NW I/O device 130 andstorage device(s) 142 controlled by storage controller 140. Facilitationof movement of data between NW I/O device 130 and storage device(s) 142may include buffer manager 116 maintaining at least some mappinginformation to map commands associated with the movement to one or morestorage devices included in storage device(s) 142.

According to some examples, NW I/O device 130, as shown in FIG. 1,includes circuitry 132 and memory 134. For these examples, logic and/orfeatures incorporated in various modules may be executed by circuitry132 to utilize buffers 115-1 to 115-m of last level cache 114 tofacilitate movement of data either read from storage device(s) 142 or tobe written/stored to storage device(s) 142. The data movement may beresponsive to data frames received from remote device(s) 170 that mayinclude requests to access storage device(s) 142 via a read request or awrite/storage request. Also, memory 134 at NW I/O device 130 may bearranged to store firmware or software implemented by the variousmodules or to at least temporarily maintain data associated with dataframes received from remote device(s) 170.

In some examples, logic and/or features at NW I/O device 130 may becapable of tagging one or more of buffers 115-1 to 115-m to indicate useof the one or more buffers for staging or at least temporarily storingdata received or transmitted via one or more network connections routedbetween NW I/O device 130 and remote device(s) 170 through network 150.For these examples, rather than using system memory (not shown) at hostdevice 105, buffers 115-1 to 115-m in last level cache 114 may beutilized to quickly move data between storage device(s) 142 and NW I/Odevice 130 with the assistance of buffer manager 116. The tagging ofbuffers 115-1 to 115-m may include the logic and/or features of NW I/Odevice 130 assigning an identifier to one or more of the buffers toindicate use of the one or more tagged buffers for accessing storagedevice 142. For example, buffer 115-1 may be tagged and a givenidentifier for this tagged buffer may be communicated to buffer manager116. Subsequently when a request to access storage device(s) 142 isreceived in a data frame sent by remote device(s) 170 and received by NWI/O device 130, the given identifier may enable buffer manager 116 toquickly identify the particular buffer to use to stage data to bepossibly moved based on the request. Also, buffer manager 116 may becapable of reviewing the request to determine whether the request is fora read or a write access and stage the data accordingly.

According to some examples, a data frame may be received at NW I/Odevice 130 from a remote device from among remote device(s) 170. Forthese examples, the data frame may include a request by the remotedevice to access storage device(s) 142. Logic and/or features at NW I/Odevice 130 may then forward to or receive from the one or more taggedbuffers data associated with the request based on whether the request isto read the data from storage device(s) 142 or is to store the data tostorage device(s) 142. For example, if the request is to read data fromstorage device(s) 142, then the data may be staged in the tagged buffer(e.g., buffer 115-1) and then received from this tagged buffer by logicand/or features of NW I/O device 130 and then transmitted to the remotedevice that made the request. Alternatively, if the request is to storedata to storage device(s) 142, then the data may be included in the dataframe received from the remote device. This data may then be forwardedto the tagged buffer by logic and/or features of NW I/O device 130 forstaging of the data for eventual storage at storage device(s) 142. Insome examples, buffer manager 116, based on control information for therequest, may reformat the request such that storage controller 140 canrespond and fulfill the request accordingly.

In some examples, communication links 135 and 145 that couple NW I/Odevice 130 and storage controller 140 to host device 105 may be capableof operating in compliance with one or more industry standardsassociated with I/O interconnects to include, but not limited to, thePeripheral Component Interconnect (PCI) Express Base Specification,revision 3.0, published in November 2010 (“PCI Express” or “PCIe”).

According to some examples, storage device(s) 142 may include one ormore devices into, and/or from which, data may be stored and/orretrieved, respectively. Also, for these examples, storage device(s) 142may include non-volatile memory for the storage of data. For example,storage device(s) 142 may include, without limitation, one or morenon-volatile electro-mechanical, magnetic, optical, and/or semiconductorstorage devices. These devices may include hard disk drives (HDDs) orsolid state drives (SSDs). The SSDs may have non-volatile types ofmemory such as 3-dimensional cross-point memory, flash memory,ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS)memory, polymer memory, nanowire, ferroelectric transistor random accessmemory (FeTRAM or FeRAM), nanowire or electrically erasable programmableread-only memory (EEPROM).

According to some examples, storage controller 140, storage devices 142and communication link 145 may be capable of operating in compliancewith the PCIe Specification, as well as with other industry standardsassociated with accessing non-volatile memory types of storage such asSSDs using a PCIe compliant communication link and/or protocols. Theseother industry standards may include, but are not limited to, theNon-Volatile Memory Express (NVMe) Specification, revision 1.1.,published in October 2012. Storage controller 140, storage devices 142and communication link 145 may also be capable of operating incompliance with other industry standards that may include, but are notlimited to, the Serial ATA (SATA) Specification, revision 3.1, publishedin July 2001, the Serial Attached SCSI (SAS) Specification, revision2.1, published in December 2010 and/or Internet SCSI (iSCSI), Requestfor Comments 3720, published in April 2004.

In some examples, communication channel 140 may include one or morecommunication links via which NW I/O device 130 may couple to network150 and establish one or more network connections to remote device(s)that couple to network 150 via communication channel 160 that also mayhave one or more communication links. These communication links includedin communication channel 140 or 160 may include various types of wired,wireless or optical communication mediums. For these examples, thecommunication links may be operated in accordance with one or moreapplicable communication or networking standards in any version. Forexample, the communication links may operate in compliance with one ormore promulgated standards or specifications for wired or wirelessnetworks by the Institute of Electrical Engineers (IEEE). Thesestandards are specifications may include, but are not limited to, IEEE802.11-2012 Standard for Information technology—Telecommunications andinformation exchange between systems—Local and metropolitan areanetworks—Specific requirements Part 11: WLAN Media Access Controller(MAC) and Physical Layer (PHY) Specifications, published March 2012,and/or later versions of this standard (“IEEE 802.11”) for wirelessmediums or IEEE 802.3-2008, Carrier sense Multiple access with CollisionDetection (CSMA/CD) Access Method and Physical Layer Specifications,Published in December 2008 (hereinafter “IEEE 802.3”) for wired mediums.

In some examples, NW I/O device 130 and remote device(s) 170 mayexchange data frames via network 150 in accordance with one or moreprotocols that may comply and/or be compatible with various types ofremote direct memory access (RDMA) protocols such as internet wide areaRDMA protocol (iWARP), Infiniband (IB) protocol, Ethernet protocol,transmission control protocol/internet protocol (TCP/IP) protocol and/orRDMA over converged Ethernet (RoCE) protocol. For example, the iWARPprotocol may comply and/or be compatible with Recio et al., “An RDMAProtocol Specification,” Internet Draft Specification, InternetEngineering Task Force (IETF), 21 Oct. 2002. Additionally, for example,the TCP/IP protocol may comply and/or be compatible with the protocolsdescribed in Internet Engineering Task Force (IETF) Request For Comments(RFC) 791 and 793, published September 1981. Also, the IB protocol maycomply and/or be compatible with Infiniband™ Architecture Specification,Vol. 2, Rel. 1.3, published November 2012. Additionally, for example,the RoCE protocol may comply and/or be compatible with Supplement toInfiniband Architecture Specification, Vol. 1, Rel. 1.2.1, Annex A16:“RDMA over Converged Ethernet (RoCE)”, published April 2010. NW I/Odevice 130 and remote device(s) 170 may also exchange data frames vianetwork 150 in accordance with one or more protocols that mayencapsulate Fibre Channel frames over Ethernet networks referred to asfiber channel over Ethernet (FCoE). FCoE may be compatible with theprotocols described in drafted by the American National Standard ofAccredited Standards Committee INCITS T11 Technical Committee, FibreChannel Backbone-5(FC-BB-5) Standard, Revision 2.0, published June 2009.Many different, additional, and/or other protocols may be used for suchexchange of data frames without departing from these examples (e.g.,earlier and/or later-developed versions of the aforesaid, related,and/or other protocols).

FIG. 2 illustrates a second example system. As shown in FIG. 2, thesecond example includes a system 200. According to some examples, system200 includes a host device 205 coupled to a NW I/O device 230 via acommunication link 235. In some examples, remote device(s) 270 mayestablish one or more network connections through communication channel260 coupled to network 250 and through communication channel 240 coupledto NW I/O device 230. For these examples, the one or more networkconnections between remote device(s) 270 and NW I/O device 230 may beused to receive data frames including requests to access a storagesubsystem (e.g., storage subsystem 236) maintained and/or unified withNW I/O device 230.

According to some examples, NW I/O device 230 may integrate both networkand storage subsystems. As a result of integrating network and storagesubsystems, requests for access to storage subsystem 236 may come fromeither host device 205 via communication link 235 or from remotedevice(s) 270 via one or more network connections routed overcommunication channel 240. For these examples, rather than staging datafor requests made by remote device(s) 270 at one or more buffers at alast level cache (e.g., buffers 215-1 to 215-m of last level cache214)), the one or more buffers may be used to exchange controlinformation for the request (e.g., data frame header information). Datamay still be staged at the one or more buffers for requests originatingfrom host device 205 (e.g., from application(s) 224). Regardless of thesource of the requests, both movements of the data do not include use ofsystem memory (e.g., included in memory 220) for moving data between therequestor and the storage subsystem for which the requestor is seekingaccess.

In some examples, as shown in FIG. 2, host device 205 includes aprocessor socket 210 including similar components or features asmentioned for FIG. 1's host device 105. For example, processor socket210 includes processor circuitry 212 having processing elements 212-1 to212-n and a buffer manager 216. Processor socket 210 may also include alast level cache 214 having buffers 215-1 to 215-n.

According to some examples, host device 205 may include a memory 220coupled to processor socket 210 via memory channel 215. For theseexamples, a protocol stack 222 and application(s) 224 may be maintainedin memory 220 and may be capable of being executed by processorcircuitry 212. Protocol stack 222 may include protocol processingsoftware configured or arranged to process control informationassociated with data frames including requests to access a storagesubsystem such as storage subsystem 236 that may include an SSD 237located at NW I/O device 230. In some examples, the data frames mayoriginate from logic and/or features of host device 205 such as fromapplication(s) 224 or may originate from remote device(s) 270. The dataframes may include control information via which protocol stack 222 mayenable host device 205 to accept or deny a request to access storagesubsystem 236.

According to some examples, logic and/or features incorporated invarious modules may be executed by circuitry 232 at NW I/O device 230.One or more of these modules may utilize one or more buffers 215-1 to215-m to exchange control information with protocol stack 222. Forexample, a data frame may be received at I/O device 230 from remotedevice(s) 270 that has control information in the form of a header forthe data frame and may also include data in a data payload. For thisexample, the control information included in the header may be sent toone or more buffers 215-1 to 215-m. Buffer manager 216 may thenfacilitate the exchange of that control information between protocolstack 222 and the one or more modules. A determination may then be madebased on the exchanged information as to whether a request included inthe data frame is for reading data from or storing data to storagesubsystem 236.

In some examples, a common or same protocol format may be used for dataframes received either from logic and/or features of host device 205 viacommunication link 235 or from remote device(s) 270 via a networkconnection routed through communication channel 240. The same protocolformat may include such protocols as FCoE, iWARP, Infiniband or RoCE.For these examples, the various modules executed by circuitry 232 at NWI/O device 230 may receive requests to access storage subsystem 236 thatare encapsulated using a same protocol format whether from a localconnection such as communication link 235 or via a network connectionrouted through communication channel 240 to network 250.

In some examples, similar to system 100's communication links 135 and145, communication link 235 of system 200 may be capable of operating incompliance with one or more industry standards or specificationsassociated with I/O interconnects to include PCIe. Also, one or more ofthe modules to be executed by circuitry 232 at NW I/O controller 230 andat least SSD 237 of storage subsystem 236 may be capable of operating incompliance with the NVMe specification. Also, communication channels 240or 260 may include various types of wired, wireless or opticalcommunication mediums. For these examples, the communication mediums aswell as network 250 may be operated in accordance with one or moreapplicable communication or networking standards in any version toinclude, but not limited to, IEEE 802.11 or IEEE 802.3 to name a few.

FIG. 3 illustrates an example process 300. In some examples, elements ofsystems 100 or 200 as shown in FIG. 1 or 2 may be used to illustrateexample operations related to the flow chart for process 300 depicted inFIG. 3. The described example operations are not limited toimplementations on systems 100 or 200 described in FIG. 1 or 2.

Moving from the start to decision block 310 (Data Frame from Host orRemote Device?), a data frame including a request to access storagesubsystem 236 may be received from either host device 205 or from remotedevice(s) 270. According to some examples, a request to access storagesubsystem 236 may originate from application(s) 224 and thus the dataframe is deemed as from host device 205. For these examples, the processmoves to block 320. Otherwise, if the data frame is received from remotedevice(s) 270 the process moves to block 350.

Moving from decision block 310 to block 320 (Host Creates ControlInformation for Data Frame), protocol stack 222 may create controlinformation for a data frame that includes a request for application(s)224 to access storage subsystem 236. In some examples, elements of hostdevice 205 may first validate/authenticate the request and then createthe control information once the request has been validated, e.g.,application(s) 224 has adequate access privileges to access storagesubsystem 236. For these examples, the control information may beassociated with a protocol format commonly being used for data framesincluding request to access storage subsystem 236. For example, thecommon protocol format may be associated with FCoE, iWARP, Infiniband orRoCE. The control information, for example, may be part of a header forthe data frame that is to be routed to NW I/O device 230.

Proceeding from block 320 to block 330 (Exchange Control Information),control information may be for the data frame from application(s) 224that may be exchanged between protocol stack 222 and logic and/orfeatures of NW I/O device 230. According to some examples, one or morebuffers 215-1 to 215-m may be utilized to exchange the controlinformation. For example, the control information may include anindication of whether applications(s) 224 has requested read access orstorage access to storage subsystem 236 and also may include furtherdetails as to what data is to be read or how much data is to be stored.NW I/O device 230 may also provide information to indicate whetherstorage subsystem 236 has an ability to meet the access request.

Proceeding from block 330 to block 340 (Host Appends Data as Necessary),protocol stack 222 may append or add data associated with the request tothe data frame. In some examples, if the request is for read access tostorage subsystem 236 no data may be appended. Alternatively, if therequest is for storage access, the data to be stored to storagesubsystem 236 may be appended to the data frame.

Moving from decision block 310 to block 350 (NW I/O Device SplitsControl Information and Data), logic and/or features at NW I/O device230 may split control information from the data frame received fromremote device(s) 270. According to some examples, the controlinformation may be included in a header portion of the data frame. Forthese examples, the data frame may be in the common protocol format usedfor requests to access storage subsystem 236. For example, as mentionedabove, the common protocol format may be associated with FCoE, iWARP,Infiniband or RoCE.

Proceeding from block 350 to block 360 (Exchange Control Information),logic and/or features at NW I/O device 230 may exchange the split outcontrol information with protocol stack 222 at host device 205. In someexamples, as mentioned above, one or more buffers 215-1 to 215-m may beutilized to exchange the control information. For example, the controlinformation may include an indication of whether remote device(s) 270has requested read access or storage access to storage subsystem 236 andalso may include further details as to what data is to be read or howmuch data is to be stored. NW I/O device 230 may also provideinformation to indicate whether storage subsystem 236 has an ability tomeet the access request.

Proceeding from block 360 to block 370 (Temporarily Store DataAssociated with the Request), logic and/or features at NW I/O device 230may store data associated with the request. In some examples, the datamay be at least temporarily stored at memory 236 if the data framereceived from remote device(s) 270 includes data to be stored to storagesubsystem 236. For these examples, the data may be only temporarilystored to wait for a response to the request based on the informationexchanged at block 360.

Moving from either block 340 or block 370 (Host Response for RequestArrives), protocol stack 222 may send a response to the request toaccess storage subsystem 236 included in the data frame received at NWI/O device 230. According to some examples, the response may be based onthe information exchanged at either block 330 or block 360.

Proceeding from block 375 to decision block 385 (Request Accepted?),logic and/or features at NW I/O device 230 may determine whether or notthe request has been accepted for access to storage subsystem 236. Insome examples, the request may be accepted based on the controlinformation exchanged indicating that storage subsystem 236 has anability to service the request (e.g., has space available, has the datarequested or the requester has adequate access rights). If the requestis accepted the process moves to block 390. Otherwise the process movesto block 395.

Moving from decision block 385 to block 390 (Cause Request to beFulfilled), the request included in the received data frame is caused tobe fulfilled and the process comes to an end. According to someexamples, logic and/or features at NW I/O device 230 may cause acontroller (not shown) included with or at storage devices withinstorage subsystem 236 (e.g., with SSD 237) to fulfill the accessrequest. For examples where the request is from application(s) 224 tostore data, the logic and/or features at NW I/O device may utilize oneor more buffers 215-1 to 215-m to receive or pull data staged ortemporarily stored to these buffers by application(s) 224. For exampleswhere the request is a storage request from remote device(s) 270, thelogic and/or features may pull the data from memory 237 that wasutilized to temporarily store the data included in a data frame receivedfrom remote device(s). Also, for examples where the request is a readrequest from application(s) 224 to read data from storage subsystem 236,the read data may be pushed or staged to one or more buffers 215-1 to215-m. Also, for examples where the request is a read request fromremote device(s) 270, the read data may be included in a data frame andsent to remote device(s) 270 via the network connection routed overcommunication channels 240 and 260 and through network 250.

Moving from decision block 385 to block 395 (Discard Data/Data Frame),the data and/or the data frame may be discarded if the request foraccess to storage subsystem 236 is rejected and the process comes to anend. In some examples, any data temporarily stored to memory 236 from adata frame received from remote device(s) 270 may be discarded. In otherexamples, any data possibly staged from application(s) 224 to any ofbuffers 215-1 to 215-m may be discarded.

FIG. 4 illustrates an example block diagram of an apparatus 400.Although apparatus 400 shown in FIG. 4 has a limited number of elementsin a certain topology, it may be appreciated that the apparatus 400 mayinclude more or less elements in alternate topologies as desired for agiven implementation.

The apparatus 400 may be supported by circuitry 420 maintained at a NWI/O device coupled to a host device (e.g., circuitry 132/232 of NW I/Odevice 130/230). Circuitry 420 may be arranged to execute one or moresoftware or firmware implemented components or modules 422-a. It isworthy to note that “a” and “b” and “c” and similar designators as usedherein are intended to be variables representing any positive integer.Thus, for example, if an implementation sets a value for a=6, then acomplete set of software or firmware for modules 422-a may includemodules 422-1, 422-2, 422-3, 422-4, 422-5 or 422-6. The examplespresented are not limited in this context and the different variablesused throughout may represent the same or different integer values.

According to some examples, circuitry 420 may include a processor orprocessor circuitry. The processor or processor circuitry can be any ofvarious commercially available processors, including without limitationan AMD® Athlon®, Duron® and Opteron® processors; ARM® application,embedded and secure processors; IBM® and Motorola® DragonBall® andPowerPC® processors; IBM and Sony® Cell processors; Intel® Atom®,Celeron®, Core (2) Duo®, Core i3, Core i5, Core i7, Itanium®, Pentium®,Xeon®, Xeon Phi® and XScale® processors; and similar processors.According to some examples circuitry 420 may also be an applicationspecific integrated circuit (ASIC) and at least some modules 422-a maybe implemented as hardware elements of the ASIC.

According to some examples, apparatus 400 may include a tag module 422-1for execution by circuitry 420. Tag module 422-1 may be capable oftagging one or more buffers maintained in a cache for processorcircuitry included in a processor socket at a host device coupled to aNW I/O device including apparatus 400. The tagging of the one or morebuffers may include sending identification information 405 that mayinclude one or more identifiers assigned to the one or more buffers bytag module 422-1. The identifiers may tag certain buffers as being usedfor staging data received or transmitted via one or more networkconnections coupled to the NW I/O device. The data may be associatedwith requests to access a storage device controlled by a storagecontroller coupled to the host device. For example, storage device(s)142 controlled by storage controller 140 as mentioned above for system100 shown in FIG. 1. Tag module 422-1 may be capable of at leasttemporarily storing buffer information 424-a (e.g., in a data structuresuch as a lookup table (LUT)). Buffer information 424-a may include theidentifiers assigned to the tagged buffers.

In some examples, apparatus 400 may also include a receive module 422-2for execution by circuitry 420. Receive module 422-2 may be capable ofreceiving data frame 410 for a remote device as described for system 100shown in FIG. 1 or from either one of remote device or an applicationbeing executed by processor circuitry at the host device as describedfor system 200 as shown in FIG. 2. Receive module 422-2 may be capableof at least temporarily storing protocol information 425-b (e.g., in aLUT) to facilitate receipt of data frame 410. Protocol information 425-bmay enable receive module 422-2 to at least be able to decode at leastheader portions of data frame 410 that may be in various protocolformats associated with access to a storage device or subsystem througha NW I/O device. These various protocol formats may include, but are notlimited to, FCoE, iWARP, Infiniband or RoCE protocol formats.

In some examples, apparatus 400 may also include a buffer module 422-3for execution by circuitry 420. Buffer module 422-3 may be capable ofusing the one or more buffers maintained in the cache for the processorcircuitry included in the processor socket for the host device. Buffermodule 422-3 may be used to exchange control information included incontrol information (info.) 415 with a protocol stack executed by theprocessor circuitry at the host device. The exchanged controlinformation may be for the access request included in data frame 410.Control info. 415, for example may include header information split fromdata frame 410 if a remote device had sent data frame 410 and may alsoinclude access information associated with the storage subsystem and/orstorage device via which the request for access was made. In otherexamples, if data frame 410 was from the host device (e.g., from anapplication), control info. 415 may also include access informationassociated with the storage subsystem and/or storage device via whichthe request for access was made. In yet other examples, control inform.415 may also include indications of whether the request is a read or astorage request. For all of the above examples, control informationincluded in control info. 415 may be passed between buffer module 422-3and the protocol stack using the one or more buffers (e.g., based ontagged identifiers). Eventually, based at least in part on the exchangedcontrol information included in control info. 415, request status 430may be received to indicate whether the protocol stack and/or otherelements of the host device have accepted or rejected the request toaccess the storage subsystem and/or storage device.

According to some examples, apparatus 400 may also include adetermination module 422-4 for execution by circuitry 420. Determinationmodule 422-4 may be capable of determining whether to read from or storeto the storage subsystem and/or storage device data associated with therequest. For these examples, determination module 422-4 may at leasttemporarily store control information 426-c that includes controlinformation in control info. 415 exchanged between buffer module 422-3and the protocol stack.

In some examples, apparatus 400 may also include a storage controllermodule 422-5 for execution by circuitry 420. Storage controller module422-5 may be capable of controlling access to the storage subsystemand/or storage device according to the determination made bydetermination module 422-4 and/or based also on whether the requeststatus 430 indicates acceptance of the request.

According to some examples, the exchanged control information includedin control info. 415 may indicate a read and request status 430indicates acceptance of the request. For these examples, storagecontroller module 422-5 may cause the data to be read from the storagesubsystem and/or storage device as data read 435. In some otherexamples, the exchanged control information may indicate storage andrequest status 430 indicates acceptance of the request. For these otherexamples, storage controller module 422-5 may cause data included indata to store 440 to be stored to the storage subsystem and/or storagedevice. This data included in data to store 440 may be retrieved fromeither a memory maintained at the NW I/O device (temporarily stored fromdata included in data frame 410) or may be pulled from one or morebuffers via which the data may have been staged or temporarily storedwhen received from requestors at the host device (e.g.,applications—also stored from data included in data frame 410).

According to some examples, apparatus 400 may also include a send module422-6 for execution by circuitry 420. Send module 422-6 may be capableof sending data included in data read 435 to the requestor that had sentdata frame 410. According to some examples, send module 422-6 may becapable of using protocol information 425-b to send the data include indata read 435 in a data frame that may be in protocol format which mayinclude, but is not limited to, a FCoE, a iWARP, an Infiniband or a RoCEprotocol format. The data frame may be sent to a remote device requestervia a network connection or sent to a requestor at the host device via alocal connection that couples the NW I/O device to the host device.

Included herein is a set of logic flows representative of examplemethodologies for performing novel aspects of the disclosedarchitecture. While, for purposes of simplicity of explanation, the oneor more methodologies shown herein are shown and described as a seriesof acts, those skilled in the art will understand and appreciate thatthe methodologies are not limited by the order of acts. Some acts may,in accordance therewith, occur in a different order and/or concurrentlywith other acts from that shown and described herein. For example, thoseskilled in the art will understand and appreciate that a methodologycould alternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, not all acts illustratedin a methodology may be required for a novel implementation.

A logic flow may be implemented in software, firmware, and/or hardware.In software and firmware embodiments, a logic flow may be implemented bycomputer executable instructions stored on at least one non-transitorycomputer readable medium or machine readable medium, such as an optical,magnetic or semiconductor storage. The embodiments are not limited inthis context.

FIG. 5 illustrates an example of a first logic flow. As shown in FIG. 5,the first logic flow includes logic flow 500. Logic flow 500 may berepresentative of some or all of the operations executed by one or morelogic, features, or devices described herein, such as apparatus 400.More particularly, logic flow 500 may be implemented by one or more oftag module 422-1, receive module 422-2, buffer module 422-3,determination module 422-4, storage controller module 422-5 or sendmodule 422-6.

According to some examples, logic flow 500 at block 502 may receive, ata NW I/O device coupled to a host device, a data frame including arequest to access a storage subsystem maintained at the NW I/O device,the storage subsystem including an SSD. For example, data frame 410 maybe received by receive module 422-2 and may include a request to accessa storage subsystem maintained at the NW I/O device that may includeapparatus 400.

In some examples, logic flow 500 at block 504 may utilize one or morebuffers maintained in a cache for processor circuitry included in aprocessor socket at the host device, the one or more buffers arranged toexchange control information for the request, the control informationexchanged with a protocol stack executed by the processor circuitry. Forexample, buffer module 422-3 may use the one or more buffers to exchangecontrol information included in control info. 415 with the protocolstack.

According to some examples, logic flow 500 at block 506 may thendetermine whether to read from or store to the storage subsystem dataassociated with the request based on the exchanged control information.For example, determination module 422-4 may use the control informationincluded in control info. 415 to make the determination as to the typeof access. As mentioned above, additional modules of apparatus 400 maythen facilitate access to the storage subsystem and cause data to bestored to or read from the storage subsystem.

FIG. 6 illustrates an example of a second logic flow. As shown in FIG.6, the second logic flow includes logic flow 600. Logic flow 600 may berepresentative of some or all of the operations executed by one or morelogic, features, or devices described herein, such as apparatus 400.More particularly, logic flow 600 may be implemented by one or more oftag module 522-1, receive module 522-2, buffer module 522-3,determination module 522-4, storage controller module 522-5 or sendmodule 522-6.

According to some examples, logic flow 600 at block 602 may tag one ormore buffers maintained in a cache for processor circuitry included in aprocessor socket at a host device. For these examples, the one or morebuffers may be tagged by a NW I/O device including apparatus 500 thatmay be coupled to the host device to indicate use of the one or morebuffers for staging data received or transmitted via one or more networkconnections coupled to the NW I/O device, the data associated withrequests to access a storage device controlled by a storage controllercoupled to the host device. For example, tag module 522-1 may providetag identification information 505 to tag the one or more buffers foruse to stage received data.

In some examples, logic flow 600 at block 604 may receive a data frameincluding a request by a remote device to access the storage device. Forexample, receive module 522-2 may receive data frame 510 that includethe request by the remote device.

According to some examples, logic flow 600 at block 606 may then forwardto or receive from the one or more tagged buffers data associated withthe request based on whether the request is to read the data from thestorage device or is to store the data to the storage device. Forexample, determination module 522-4 may determine whether the accessrequest included in data frame 510 is for a read or a store to thestorage device. As a result of a determination of a read, storagecontroller module 422-5 may cause data included in data read 435 to beread from the storage device and this data may be staged to the one ormore tagged buffers. Buffer module 422-3 may then pull the data includedin data read 435 from the one or more tagged buffers and provide thedata to send module 422-6. Send module 422-6 may then send the dataincluded in data read 435 to the remote device. Alternatively, as aresult of a determination of a store, buffer module 422-3 may stage dataincluded in data to store 440 to the tagged one or more buffers. Forthis alternative, the staged data may have been obtained from data frame410. Storage controller module 422-5 may then cause this staged dataincluded in data to store 440 to be stored to storage device.

FIG. 7 illustrates an example of a computer readable medium 700.Computer readable medium 700 may comprise an article of manufacture. Insome examples, computer readable medium 700 may include anynon-transitory computer readable medium or machine readable medium, suchas an optical, magnetic or semiconductor storage. Computer readablemedium 700 may store various types of computer executable instructions,such as instructions to implement logic flow 500 or logic flow 600.Examples of a computer readable or machine readable storage medium mayinclude any tangible media capable of storing electronic data, includingvolatile memory or non-volatile memory, removable or non-removablememory, erasable or non-erasable memory, writeable or re-writeablememory, and so forth. Examples of computer executable instructions mayinclude any suitable type of code, such as source code, compiled code,interpreted code, executable code, static code, dynamic code,object-oriented code, visual code, and the like. The examples are notlimited in this context.

FIG. 8 illustrates an example NW I/O device 800. In some examples, asshown in FIG. 8, NW I/O device 800 may include a processing component840, other platform components or a communications interface 860.According to some examples, NW I/O device 800 may be implemented in a NWI/O device coupled to a host or client device as mentioned above. Insome examples, NW I/O device 800 may or may not include a storagesubsystem that further includes a storage device such as an SSD.

According to some examples, processing component 840 may executeprocessing operations or logic for apparatus 400 and/or computerreadable medium 700. Processing component 840 may include varioushardware elements, software elements, or a combination of both. Examplesof hardware elements may include devices, logic devices, components,processors, microprocessors, circuits, processor circuits, circuitelements (e.g., transistors, resistors, capacitors, inductors, and soforth), integrated circuits, application specific integrated circuits(ASIC), programmable logic devices (PLD), digital signal processors(DSP), field programmable gate array (FPGA), memory units, logic gates,registers, semiconductor device, chips, microchips, chip sets, and soforth. Examples of software elements may include software components,programs, applications, computer programs, application programs, devicedrivers, system programs, software development programs, machineprograms, operating system software, middleware, firmware, softwaremodules, routines, subroutines, functions, methods, procedures, softwareinterfaces, application program interfaces (API), instruction sets,computing code, computer code, code segments, computer code segments,words, values, symbols, or any combination thereof. Determining whetheran example is implemented using hardware elements and/or softwareelements may vary in accordance with any number of factors, such asdesired computational rate, power levels, heat tolerances, processingcycle budget, input data rates, output data rates, memory resources,data bus speeds and other design or performance constraints, as desiredfor a given example.

In some examples, other I/O components 850 may include withoutlimitation various types of storage mediums in the form of one or morehigher speed memory units, such as ROM, RAM, DRAM, DDRAM, SDRAM, SRAM,PROM, EPROM, EEPROM, flash memory or any other type of storage mediasuitable for storing information.

In some examples, communications interface 860 may include logic and/orfeatures to support a communication interface. For these examples,communications interface 860 may include one or more communicationinterfaces that operate according to various communication protocols orstandards to communicate over direct or network communication links.Direct communications may occur via use of communication protocols orstandards described in one or more industry standards or specifications(including progenies and variants) such as those associated with thePCIe specification, the NVMe specification, the RDMA Protocolspecifications (e.g. iWARP, RoCE, Infiniband, the IEEE 802.3 or 802.11specifications, RFC 791, RFC 793 or the FCoE standard.

The components and features of NW I/O device 800 may be implementedusing any combination of discrete circuitry, application specificintegrated circuits (ASICs), logic gates and/or single chiparchitectures. Further, the features of NW I/O device 800 may beimplemented using microcontrollers, programmable logic arrays and/ormicroprocessors or any combination of the foregoing where suitablyappropriate. It is noted that hardware, firmware and/or softwareelements may be collectively or individually referred to herein as“logic” or “circuit.”

It should be appreciated that the exemplary NW I/O device 800 shown inthe block diagram of FIG. 8 may represent one functionally descriptiveexample of many potential implementations. Accordingly, division,omission or inclusion of block functions depicted in the accompanyingfigures does not infer that the hardware components, circuits, softwareand/or elements for implementing these functions would necessarily bedivided, omitted, or included in embodiments.

It should be appreciated that the exemplary NW I/O device 800 shown inthe block diagram of FIG. 8 may represent one functionally descriptiveexample of many potential implementations. Accordingly, division,omission or inclusion of block functions depicted in the accompanyingfigures does not infer that the hardware components, circuits, softwareand/or elements for implementing these functions would necessarily bedivided, omitted, or included in embodiments.

One or more aspects of at least one example may be implemented byrepresentative instructions stored on at least one machine-readablemedium which represents various logic within the processor, which whenread by a machine, computing device or system causes the machine,computing device or system to fabricate logic to perform the techniquesdescribed herein. Such representations, known as “IP cores” may bestored on a tangible, machine readable medium and supplied to variouscustomers or manufacturing facilities to load into the fabricationmachines that actually make the logic or processor.

Various examples may be implemented using hardware elements, softwareelements, or a combination of both. In some examples, hardware elementsmay include devices, components, processors, microprocessors, circuits,circuit elements (e.g., transistors, resistors, capacitors, inductors,and so forth), integrated circuits, application specific integratedcircuits (ASIC), programmable logic devices (PLD), digital signalprocessors (DSP), field programmable gate array (FPGA), memory units,logic gates, registers, semiconductor device, chips, microchips, chipsets, and so forth. In some examples, software elements may includesoftware components, programs, applications, computer programs,application programs, system programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces,application program interfaces (API), instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof. Determining whether an example isimplemented using hardware elements and/or software elements may vary inaccordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherdesign or performance constraints, as desired for a givenimplementation.

Some examples may include an article of manufacture or at least onecomputer-readable medium. A computer-readable medium may include anon-transitory storage medium to store logic. In some examples, thenon-transitory storage medium may include one or more types ofcomputer-readable storage media capable of storing electronic data,including volatile memory or non-volatile memory, removable ornon-removable memory, erasable or non-erasable memory, writeable orre-writeable memory, and so forth. In some examples, the logic mayinclude various software elements, such as software components,programs, applications, computer programs, application programs, systemprograms, machine programs, operating system software, middleware,firmware, software modules, routines, subroutines, functions, methods,procedures, software interfaces, API, instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof.

According to some examples, a computer-readable medium may include anon-transitory storage medium to store or maintain instructions thatwhen executed by a machine, computing device or system, cause themachine, computing device or system to perform methods and/or operationsin accordance with the described examples. The instructions may includeany suitable type of code, such as source code, compiled code,interpreted code, executable code, static code, dynamic code, and thelike. The instructions may be implemented according to a predefinedcomputer language, manner or syntax, for instructing a machine,computing device or system to perform a certain function. Theinstructions may be implemented using any suitable high-level,low-level, object-oriented, visual, compiled and/or interpretedprogramming language.

Some examples may be described using the expression “in one example” or“an example” along with their derivatives. These terms mean that aparticular feature, structure, or characteristic described in connectionwith the example is included in at least one example. The appearances ofthe phrase “in one example” in various places in the specification arenot necessarily all referring to the same example.

Some examples may be described using the expression “coupled” and“connected” along with their derivatives. These terms are notnecessarily intended as synonyms for each other. For example,descriptions using the terms “connected” and/or “coupled” may indicatethat two or more elements are in direct physical or electrical contactwith each other. The term “coupled,” however, may also mean that two ormore elements are not in direct contact with each other, but yet stillco-operate or interact with each other.

In some examples, an example apparatus for a network I/O device coupledto a host device may include circuitry. The example first apparatus mayalso include a receive module for execution by the circuitry to receivea data frame that includes a request to access a storage subsystemmaintained at the network I/O device. The storage subsystem may includean SSD. The example first apparatus may also include a buffer module forexecution by the circuitry to use one or more buffers maintained in acache for processor circuitry included in a processor socket at the hostdevice. The one or more buffers may be used to exchange controlinformation for the request. the control information may be exchangedwith a protocol stack executed by the processor circuitry. The examplefirst apparatus may also include a determination module for execution bythe circuitry to determine whether to read from or store to the storagesubsystem data associated with the request based on the exchangedcontrol information.

According to some examples, the example apparatus may also include astorage controller module to control access to the storage subsystembased on the determination by the determination module.

In some examples for the example apparatus, the storage controllermodule and at least the SSD may be arranged to operate in compliancewith one or more industry standards to include PCIe Base Specification,revision 3.0 or NVMe Specification, revision 1.1.

According to some examples for the example apparatus, the receive modulemay receive the data frame from the host device via a local connectionwith the host device or from a remote device via a network connectionwith the remote device, the data frame configured in compliance with asame protocol format whether received from the host device or the remotedevice.

In some examples for the example apparatus, the same protocol format mayinclude FCoE, iWARP, Infiniband or RoCE.

According to some examples for the example apparatus, the receive modulemay receive the data frame from the host device and the request includedin the data frame is for an application executed by the processorcircuitry to access the storage subsystem.

According to some examples for the example apparatus, the request fromthe application may store data associated with the data frame to thestorage subsystem. The data at least temporarily stored to the one ormore buffers prior to fulfilling the request to store the data to thestorage subsystem.

In some examples for the example apparatus, the request from theapplication may read data from the storage subsystem. The read data atleast temporarily stored to the one or more buffers after fulfilling therequest to read the data from the storage subsystem.

According to some examples for the example apparatus, the controlinformation for the request may include header information associatedwith the data frame to facilitate a determination by the protocol stackexecuted by the processor circuitry as to whether to accept or deny therequest.

In some examples for the example apparatus, the receive module mayreceive the data frame from the remote device and the request may be forthe remote device to store data associated with the data frame to thestorage subsystem. The data at least temporarily stored to a memorymaintained at the network I/O device and then caused to be stored to thestorage subsystem following acceptance of the request.

According to some examples for the example apparatus, the receive modulemay receive the data frame from the remote device and the request is forthe remote device to read data from the storage subsystem.

In some examples, the example apparatus may also include a send modulefor execution by the circuitry to send the read data to the remotedevice via the network connection following acceptance of the request.

According to some examples for the example apparatus, the localconnection with the host device may be arranged to operate in compliancewith one or more industry standards including PCIe Base Specification,revision 3.0.

In some examples, example first methods implemented at a network I/Odevice coupled to a host device may include receiving a data frameincluding a request to access a storage subsystem maintained at thenetwork I/O device. For these examples, the storage subsystem mayinclude an SSD. The example first methods may also include utilizing oneor more buffers maintained in a cache for processor circuitry includedin a processor socket at the host device. The one or more buffers may bearranged to exchange control information for the request. The controlinformation may be exchanged with a protocol stack executed by theprocessor circuitry. The example first methods may also includedetermining whether to read from or store to the storage subsystem dataassociated with the request based on the exchanged control information.

According to some examples for the example first methods, the data framemay be received from the host device via a local connection with thehost device or from a remote device via a network connection with theremote device. For these examples, the data frame may be configured incompliance with a same protocol format whether received from the hostdevice or the remote device.

In some examples for the example first methods, the same protocol formatmay include FCoE, iWARP, Infiniband or RoCE.

According to some examples for the example first methods, the data framemay be received from the host device and the request included in thedata frame is for an application executed by the processor circuitry toaccess the storage subsystem.

In some examples for the example first methods, the request from theapplication may be to store data associated with the data frame to thestorage subsystem. The data at least temporarily stored to the one ormore buffers prior to fulfilling the request to store the data to thestorage subsystem.

According to some examples for the example first methods, the requestfrom the application may be to read data from the storage subsystem. Theread data at least temporarily stored to the one or more buffers afterfulfilling the request to read the data from the storage subsystem.

In some examples for the example first methods, the control informationfor the request to include header information associated with the dataframe may be to facilitate a determination by the protocol stackexecuted by the processor circuitry as to whether to accept or deny therequest.

According to some examples for the example first methods, the data framemay be received from the remote device and the request is for the remotedevice to store data associated with the data frame to the storagesubsystem. The data at least temporarily stored to a memory maintainedat the network I/O device and then stored to the storage subsystemfollowing acceptance of the request.

In some examples for the example first methods, the data frame may bereceived from the remote device and the request is for the remote deviceto read data from the storage subsystem. For these examples, the readdata may be sent to the remote device via the network connectionfollowing acceptance of the request.

According to some examples for the example first methods, the SSDincluded in the storage subsystem may have non-volatile memory thatincludes at least one of 3-dimensional cross-point memory, flash memory,ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS)memory, polymer memory, nanowire, ferroelectric transistor random accessmemory (FeTRAM or FeRAM), nanowire or electrically erasable programmableread-only memory (EEPROM).

In some examples for the example first methods, the local connectionwith the host device may be arranged to operate in compliance with oneor more industry standards including PCIe Base Specification, revision3.0.

In some examples, a first at least one machine readable mediumcomprising a plurality of instructions that in response to beingexecuted on a network I/O device coupled to a host device causes thenetwork I/O device to receive a data frame including a request to accessa storage subsystem maintained at the network I/O device, the storagesubsystem including an SSD. The instructions may also cause the networkI/O device to utilize one or more buffers maintained in a cache forprocessor circuitry included in a processor socket at the host device.The one or more buffers may be arranged to exchange control informationfor the request. The control information may be exchanged with aprotocol stack executed by the processor circuitry. The instructions mayalso cause the network I/O device to determine whether to read from orstore to the storage subsystem data associated with the request based onthe exchanged control information.

According to some examples for the first at least one machine readablemedium, the data frame may be received from the host device via a localconnection with the host device or from a remote device via a networkconnection with the remote device. The data frame may be configured incompliance with a same protocol format whether received from the hostdevice or the remote device.

In some examples for the first at least one machine readable medium, thesame protocol format to may include FCoE, iWARP, Infiniband or RoCE.

According to some examples for the first at least one machine readablemedium, the data frame may be received from the host device and therequest included in the data frame is for an application executed by theprocessor circuitry to access the storage subsystem.

In some examples for the first at least one machine readable medium, therequest from the application may be to store data associated with thedata frame to the storage subsystem. For these examples, the data atleast temporarily stored to the one or more buffers prior to fulfillingthe request to store the data to the storage subsystem.

According to some examples for the first at least one machine readablemedium, the request from the application may be to read data from thestorage subsystem. The read data at least temporarily stored to the oneor more buffers after fulfilling the request to read the data from thestorage subsystem.

In some examples for the first at least one machine readable medium, thecontrol information for the request may include header informationassociated with the data frame to facilitate a determination by theprotocol stack executed by the processor circuitry as to whether toaccept or deny the request.

According to some examples for the first at least one machine readablemedium, the data frame may be received from the remote device and therequest is for the remote device to store data associated with the dataframe to the storage subsystem. The instructions may also cause thenetwork I/O device to at least temporarily store the data to a memorymaintained at the network I/O device and then cause the data to bestored to the storage subsystem following acceptance of the request.

In some examples for the first at least one machine readable medium, thedata frame may be received from the remote device and the request is forthe remote device to read data from the storage subsystem. Theinstructions may also cause the network I/O device to send the read datato the remote device via the network connection following acceptance ofthe request.

According to some examples for the first at least one machine readablemedium, the local connection with the host device may be arranged tooperate in compliance with one or more industry standards including PCIeBase Specification, revision 3.0.

In some examples, example second methods implemented at a network I/Odevice coupled to a host device may include tagging one or more buffersmaintained in a cache for processor circuitry included in a processorsocket at the host device. The one or more buffers may be tagged by anetwork I/O device coupled to the host device to indicate use of the oneor more buffers for staging data received or transmitted via one or morenetwork connections coupled to the network I/O device. The data may beassociated with requests to access a storage device controlled by astorage controller coupled to the host device. The example secondmethods may also include receiving a data frame including a request by aremote device to access the storage device. The example second methodsmay also include forwarding to or receiving from the one or more taggedbuffers data associated with the request based on whether the request isto read the data from the storage device or is to store the data to thestorage device.

According to some examples for the example second methods, tagging theone or more buffers may include assigning an identifier to the one ormore buffers to indicate use of the one or more tagged buffers foraccessing the storage device based on one or more requests included inone or more data frames received from the remote device.

In some examples for the example second methods, the storage deviceinclude an SSD and the storage controller and the SSD may be arranged tooperate in compliance with one or more industry standards to includePCIe Base Specification, revision 3.0 or NVMe Specification, revision1.1.

According to some examples for the example second methods, the SSDhaving non-volatile memory that includes at least one of 3-dimensionalcross-point memory, flash memory, ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, polymer memory,nanowire, ferroelectric transistor random access memory (FeTRAM orFeRAM), nanowire or electrically erasable programmable read-only memory(EEPROM).

In some examples for the example second methods, the data frame may beconfigured in compliance with a protocol format to include FCoE, iWARP,Infiniband or RoCE.

In some examples, a second at least one machine readable mediumcomprising a plurality of instructions that in response to beingexecuted on a network I/O device coupled to a host device causes thenetwork I/O device to tag one or more buffers maintained in a cache forprocessor circuitry included in a processor socket at a host device. Theone or more buffers may be tagged by the network I/O device to indicateuse of the one or more buffers for staging data received or transmittedvia one or more network connections coupled to the network I/O device.The data may be associated with requests to access a storage devicecontrolled by a storage controller coupled to the host device. Theinstructions may also cause the network I/O device to receive a dataframe including a request by a remote device to access the storagedevice. The instructions may also cause the network I/O device toforward to or receive from the one or more tagged buffers dataassociated with the request based on whether the request is to read thedata from the storage device or is to store the data to the storagedevice.

According to some examples for the second at least one machine readablemedium, instructions to tag the one or more buffers may include theinstructions to cause the network I/O device to assign an identifier tothe one or more buffers to indicate use of the one or more taggedbuffers for accessing the storage device based on one or more requestsincluded in one or more data frames received from the remote device.

In some examples for the second at least one machine readable medium,the storage device may include an SSD and the storage controller and theSSD may be arranged to operate in compliance with one or more industrystandards to include PCIe Base Specification, revision 3.0 or NVMeSpecification, revision 1.1.

According to some examples for the second at least one machine readablemedium, the SSD may have non-volatile memory that includes at least oneof 3-dimensional cross-point memory, flash memory, ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, polymer memory,nanowire, ferroelectric transistor random access memory (FeTRAM orFeRAM), nanowire or electrically erasable programmable read-only memory(EEPROM).

In some examples for the second at least one machine readable medium,the data frame configured in compliance with a protocol format toinclude FCoE, iWARP, Infiniband or RoCE.

It is emphasized that the Abstract of the Disclosure is provided tocomply with 37 C.F.R. Section 1.72(b), requiring an abstract that willallow the reader to quickly ascertain the nature of the technicaldisclosure. It is submitted with the understanding that it will not beused to interpret or limit the scope or meaning of the claims. Inaddition, in the foregoing Detailed Description, it can be seen thatvarious features are grouped together in a single example for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted as reflecting an intention that the claimed examplesrequire more features than are expressly recited in each claim. Rather,as the following claims reflect, inventive subject matter lies in lessthan all features of a single disclosed example. Thus the followingclaims are hereby incorporated into the Detailed Description, with eachclaim standing on its own as a separate example. In the appended claims,the terms “including” and “in which” are used as the plain-Englishequivalents of the respective terms “comprising” and “wherein,”respectively. Moreover, the terms “first,” “second,” “third,” and soforth, are used merely as labels, and are not intended to imposenumerical requirements on their objects.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

What is claimed is:
 1. An apparatus comprising: a host device comprisinga processor socket; circuitry for a network input/output (I/O) devicecoupled with the host device, the circuitry configured to: receive adata frame comprising a request to access a storage subsystem maintainedat the network I/O device, the storage subsystem comprising a solidstate drive (SSD); use one or more buffers maintained in a cache forprocessor circuitry included in the processor socket, the one or morebuffers used to exchange control information for the request with aprotocol stack executed by the processor circuitry; and determine, basedon the control information, whether to read from or store to the storagesubsystem, data associated with the request.
 2. The apparatus of claim1, comprising: a storage controller to control access to the storagesubsystem based on the determination.
 3. The apparatus of claim 2,wherein the storage controller and at least the SSD are arranged tooperate in compliance with one or more industry standards to includePCIe Base Specification, revision 3.0 or NVMe Specification, revision1.1.
 4. The apparatus of claim 1, the circuitry for the network I/Odevice configured to: receive the data frame from the host device via alocal connection with the host device or from a remote device via anetwork connection with the remote device, the data frame configured incompliance with a protocol format.
 5. The apparatus of claim 4, theprotocol format to include fiber channel over Ethernet (FCoE), internetwide area RDMA protocol (iWARP), Infiniband or RDMA over convergedEthernet (RoCE).
 6. The apparatus of claim 4, the protocol stack todetermine whether to accept or deny the request based on a header of thedata frame.
 7. The apparatus of claim 6, the circuitry for the networkI/O device configured to: receive the data frame from the remote device,wherein the request is for the remote device to store data associatedwith the data frame to the storage subsystem, the data at leasttemporarily stored to a memory maintained at the network I/O device andcaused to be stored to the storage subsystem following acceptance of therequest.
 8. The apparatus of claim 7, the circuitry for the network I/Odevice configured to: receive the data frame from the remote device,wherein the request is for the remote device to read data from thestorage subsystem.
 9. The apparatus of claim 8, the circuitry for thenetwork I/O device configured to: send the read data to the remotedevice via the network connection following acceptance of the request.10. The apparatus of claim 8, the local connection with the host devicearranged to operate in compliance with one or more industry standardsincluding PCIe Base Specification, revision 3.0.
 11. A methodcomprising: receiving, at a network input/output (I/O) device, a dataframe comprising a request to access a storage subsystem maintained atthe network I/O device, the storage subsystem comprising a solid statedrive (SSD); utilizing one or more buffers maintained in a cache forprocessor circuitry included in a processor socket at a host devicecoupled with the network I/O device, the one or more buffers arranged toexchange control information for the request with a protocol stackexecuted by the processor circuitry; and determining, based on thecontrol information, whether to read from or store to the storagesubsystem, data associated with the request.
 12. The method of claim 11,the data frame configured in compliance with a protocol format, the dataframe received from one of a host device via a local connection with thehost device and a remote device via a network connection with the remotedevice, the protocol stack to determine whether to accept or deny therequest based on a header of the data frame.
 13. The method of claim 12,the protocol format to include fiber channel over Ethernet (FCoE),internet wide area RDMA protocol (iWARP), Infiniband or RDMA overconverged Ethernet (RoCE).
 14. The method of claim 12, comprising thedata frame received from the host device and the request included in thedata frame is for an application executed by the processor circuitry toaccess the storage subsystem.
 15. The method of claim 14, comprising therequest from the application to store data associated with the dataframe to the storage subsystem, the data at least temporarily stored tothe one or more buffers prior to fulfilling the request to store thedata to the storage subsystem.
 16. The method of claim 14, comprisingthe request from the application to read data from the storagesubsystem, the read data at least temporarily stored to the one or morebuffers after fulfilling the request to read the data from the storagesubsystem.
 17. The method of claim 11, comprising the SSD included inthe storage subsystem having non-volatile memory that includes at leastone of 3-dimensional cross-point memory, flash memory, ferroelectricmemory, silicon-oxide-nitride-oxide-silicon (SONOS) memory, polymermemory, nanowire, ferroelectric transistor random access memory (FeTRAMor FeRAM), nanowire or electrically erasable programmable read-onlymemory (EEPROM).
 18. A non-transitory machine-readable medium comprisinginstructions that in response to being executed on a networkinput/output (I/O) device coupled to a host device cause the network I/Odevice to: receive a data frame comprising a request to access a storagesubsystem maintained at the network I/O device, the storage subsystemincluding a solid state drive (SSD); utilize one or more buffersmaintained in a cache for processor circuitry included in a processorsocket at the host device, the one or more buffers used to exchangecontrol information for the request with a protocol stack executed bythe processor circuitry; and determine, based on the controlinformation, whether to read from or store to the storage subsystem,data associated with the request.
 19. The machine-readable medium ofclaim 18, comprising instructions that in response to being executed onthe network I/O device cause the network I/O device to: receive the dataframe from the host device via a local connection with the host deviceor from a remote device via a network connection with the remote device,the data frame configured in compliance with a protocol format.
 20. Themachine-readable medium of claim 19, the protocol format to includefiber channel over Ethernet (FCoE), internet wide area RDMA protocol(iWARP), Infiniband or RDMA over converged Ethernet (RoCE).
 21. A methodcomprising: tagging one or more buffers maintained in a cache forprocessor circuitry included in a processor socket at a host device, theone or more buffers tagged by a network input/output (I/O) devicecoupled to the host device to indicate use of the one or more buffersfor staging data received or transmitted via one or more networkconnections coupled to the network I/O device, the data associated withrequests to access a storage device controlled by a storage controllercoupled to the host device; receiving a data frame including a requestby a remote device to access the storage device; and forwarding to orreceiving from the one or more tagged buffers data associated with therequest based on whether the request is to read the data from thestorage device or is to store the data to the storage device.
 22. Themethod of claim 21, wherein tagging the one or more buffers comprisesassigning an identifier to the one or more buffers to indicate use ofthe one or more tagged buffers for accessing the storage device based onone or more requests included in one or more data frames received fromthe remote device.
 23. The method of claim 21, wherein the storagedevice comprises a solid state drive (SSD) and the storage controllerand the SSD are arranged to operate in compliance with one or moreindustry standards to include PCIe Base Specification, revision 3.0 orNVMe Specification, revision 1.1.
 24. The method of claim 23, comprisingthe SSD having non-volatile memory that includes at least one of3-dimensional cross-point memory, flash memory, ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, polymer memory,nanowire, ferroelectric transistor random access memory (FeTRAM orFeRAM), nanowire or electrically erasable programmable read-only memory(EEPROM).
 25. The method of claim 21, the data frame configured incompliance with a protocol format, the data frame received from one of ahost device via a local connection with the host device and a remotedevice via a network connection with the remote device, the protocolformat to include fiber channel over Ethernet (FCoE), internet wide areaRDMA protocol (iWARP), Infiniband or RDMA over converged Ethernet(RoCE).